SonarSource Rules
  • Products

    In-IDE

    Code Quality and Security in your IDE with SonarQube Ide

    IDE extension that lets you fix coding issues before they exist!

    Discover SonarQube for IDE

    SaaS

    Code Quality and Security in the cloud with SonarQube Cloud

    Setup is effortless and analysis is automatic for most languages

    Discover SonarQube Cloud

    Self-Hosted

    Code Quality and Security Self-Hosted with SonarQube Server

    Fast, accurate analysis; enterprise scalability

    Discover SonarQube Server
  • SecretsSecrets
  • ABAPABAP
  • AnsibleAnsible
  • ApexApex
  • AzureResourceManagerAzureResourceManager
  • CC
  • C#C#
  • C++C++
  • CloudFormationCloudFormation
  • COBOLCOBOL
  • CSSCSS
  • DartDart
  • DockerDocker
  • FlexFlex
  • GitHub ActionsGitHub Actions
  • GoGo
  • HTMLHTML
  • JavaJava
  • JavaScriptJavaScript
  • JSONJSON
  • JCLJCL
  • KotlinKotlin
  • KubernetesKubernetes
  • Objective CObjective C
  • PHPPHP
  • PL/IPL/I
  • PL/SQLPL/SQL
  • PythonPython
  • RPGRPG
  • RubyRuby
  • RustRust
  • ScalaScala
  • SwiftSwift
  • TerraformTerraform
  • TextText
  • TypeScriptTypeScript
  • T-SQLT-SQL
  • VB.NETVB.NET
  • VB6VB6
  • XMLXML
  • YAMLYAML
Go

Go static code analysis

Unique rules to find Bugs, Vulnerabilities, Security Hotspots, and Code Smells in your GO code

  • All rules 70
  • Vulnerability20
  • Bug7
  • Security Hotspot14
  • Code Smell29
 
Tags
    Impact
      Clean code attribute
        1. Hard-coded secrets are security-sensitive

           Security Hotspot
        2. Constructing arguments of system commands from user input is security-sensitive

           Security Hotspot
        3. Using publicly writable directories is security-sensitive

           Security Hotspot
        4. Using clear-text protocols is security-sensitive

           Security Hotspot
        5. Using weak hashing algorithms is security-sensitive

           Security Hotspot
        6. Delivering code in production with debug features activated is security-sensitive

           Security Hotspot
        7. Searching OS commands in PATH is security-sensitive

           Security Hotspot
        8. Creating cookies without the "HttpOnly" flag is security-sensitive

           Security Hotspot
        9. Setting loose POSIX file permissions is security-sensitive

           Security Hotspot
        10. Using pseudorandom number generators (PRNGs) is security-sensitive

           Security Hotspot
        11. Creating cookies without the "secure" flag is security-sensitive

           Security Hotspot
        12. Formatting SQL queries is security-sensitive

           Security Hotspot
        13. Hard-coded credentials are security-sensitive

           Security Hotspot
        14. Using hardcoded IP addresses is security-sensitive

           Security Hotspot

        Searching OS commands in PATH is security-sensitive

        intentionality - complete
        security
        Security Hotspot
        • cwe

        When you run an OS command, it is always important to protect yourself against the risk of accidental or malicious replacement of the executables in the production system.

        To do so, it is important to point to the specific executable that should be used.

        For example, if you call git (without specifying a path), the operating system will search for the executable in the directories specified in the PATH environment variable.
        An attacker could have added, in a permissive directory covered by PATH , another executable called git, but with a completely different behavior, for example exfiltrating data or exploiting a vulnerability in your own code.

        However, by calling /usr/bin/git or ../git (relative path) directly, the operating system will always use the intended executable.
        Note that you still need to make sure that the executable is not world-writeable and potentially overwritten. This is not the scope of this rule.

        Ask Yourself Whether

        • The PATH environment variable only contains fixed, trusted directories.

        There is a risk if you answered no to this question.

        Recommended Secure Coding Practices

        If you wish to rely on the PATH environment variable to locate the OS command, make sure that each of its listed directories is fixed, not susceptible to change, and not writable by unprivileged users.

        If you determine that these folders cannot be altered, and that you are sure that the program you intended to use will be used, then you can determine that these risks are under your control.

        A good practice you can use is to also hardcode the PATH variable you want to use, if you can do so in the framework you use.

        If the previous recommendations cannot be followed due to their complexity or other requirements, then consider using the absolute path of the command instead.

        $ whereis git
        git: /usr/bin/git /usr/share/man/man1/git.1.gz
        $ ls -l /usr/bin/git
        -rwxr-xr-x 1 root root 3376112 Jan 28 10:13 /usr/bin/git
        

        Sensitive Code Example

        out, _ := exec.Command("ls").CombinedOutput() // Sensitive
        

        Compliant Solution

        out, _ := exec.Command("/bin/ls").CombinedOutput()
        

        See

        • OWASP - Top 10 2021 Category A8 - Software and Data Integrity Failures
        • OWASP - Top 10 2017 Category A1 - Injection
        • CWE - CWE-426 - Untrusted Search Path
        • CWE - CWE-427 - Uncontrolled Search Path Element
          Available In:
        • SonarQube IdeCatch issues on the fly,
          in your IDE
        • SonarQube CloudDetect issues in your GitHub, Azure DevOps Services, Bitbucket Cloud, GitLab repositories
        • SonarQube ServerAnalyze code in your
          on-premise CI

        © 2008-2025 SonarSource SA. All rights reserved.

        Privacy Policy | Cookie Policy | Terms of Use